Skip to content

Conversation

@LiamPhil
Copy link

Updates the chirpstack.config file to include UCI commands for the [integration.mqtt] section of the chirpstack.toml, then update the chirpstack.init to use these UCI commands when generating the runtime chirpstack.toml.

I left the tls_certificate options out as there is no easy way to upload them. The updates leave MQTT as the only enabled integration.

@brocaar
Copy link
Contributor

brocaar commented Nov 6, 2025

I understand that forwarding to an external MQTT broker could be useful for some, but within the context of the ChirpStack Gateway OS - Full image, everything is intended to run locally and thus to forward to the local MQTT broker.

These changes alone would not be enough, as users that would upgrade to these changes will have empty configuration values for these settings and thus their setup would break unless we add a migrations script that adds these config options. If the defaults would change at a later time, it would mean we would need to add a new migration script to update the defaults.

I prefer to keep things simple where we can...

@brocaar brocaar closed this Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants